Manage Agent Versions with Drafts and Publishing
Agent Version Control allows you to manage changes to your agents by separating work-in-progress drafts from what’s live in production, giving you full control over when updates are deployed.Understanding Agent Version Control
Agent Version Control distinguishes between your editable Drafts and stable Published Versions, ensuring a controlled development and deployment workflow.How it Works
- You always edit in a Draft. Drafts are user-specific, and you can maintain up to three parallel drafts simultaneously.
- Changes made in a Draft do not affect live users or automations. Your active interfaces and triggers continue to use the last Published Version.
- When you Publish, a snapshot of your current draft is created and promoted to become the active version used in production.
- Every Published Version is retained. You can restore any past version to a draft or deprecate it to hide it from the history list.
💡 Analogy: Think of a website Content Management System (CMS). A Draft is like clicking “Save Draft”—only your team can preview it. Publishing is like pushing changes to your live domain (e.g., acme.new)—everyone sees the published version.
Draft vs. Published Version
| Feature | Draft | Published Version |
|---|---|---|
| Purpose | Build, edit, and test in a safe, isolated environment. | Executes on triggers, exposes UI to users, processes webhooks. |
| Editable? | ✅ Yes – this is where all changes begin. | ❌ No – must restore to a draft first. |
| Runnable? | ✅ Yes – using the Test (Playground). | ✅ Yes – runs via triggers, interfaces, or webhooks. |
| Interfaces Accessible? | Can be configured, but not viewable by users. | ✅ Yes – users access this version. |
| Webhooks Use This? | ✅ Yes – for testing when specified in the API call. | ✅ Yes – API calls run this version. |
| Effect of Saving | All drafts are auto-saved. | Remains unchanged. |
Managing Agent Versions: Restore and Publish
Restoring a version allows you to bring a previous version into a draft for editing. Publishing makes your draft live and active.💡 Note: Restoring a version only copies its content into a draft; it does not automatically publish it. You must explicitly publish the draft to make it live.
Restore a Version to a Draft
Follow these steps to copy a previous agent version into a draft for further editing:- Click the History icon (a clock icon) in the top navigation bar.
- Locate the specific version you want to restore from the list.
- Click the More actions menu (
...) next to the desired version. - Select Restore as Draft.
- If you have multiple existing drafts or all three draft slots are currently full, you will be prompted to select which existing draft to overwrite with the restored content.
Publish a Draft to Go Live
Once your draft is ready, publish it to make it the active version for all users and automations.- Navigate to your active draft (you’ll see the Draft label prominently displayed).
- Make any necessary final changes or conduct a final review of your agent.
- Click the Publish button in the top right corner.
- Optionally, set a custom display name and add a version note to clearly describe the changes included in this version.
- Confirm the publishing action to deploy your changes.
Working with Drafts
Drafts are your personal, isolated workspaces for developing and testing agent changes without affecting live operations.- Default Draft: Each agent automatically starts with one user-specific draft.
- Create New Drafts: Click + New Draft to create additional drafts. You can have up to three drafts in parallel for complex or concurrent work.
- Overwrite Drafts: When restoring an older version, if you already have multiple drafts, you’ll be prompted to choose which draft to overwrite.
- Delete Drafts: You can delete a draft at any time when it is no longer needed.